Skip to content

Pin flowmcp-grading by commit hash (consistency) - #101

Merged
a6b8 merged 1 commit into
mainfrom
memo-110-cli-pin-hash
Jun 5, 2026
Merged

Pin flowmcp-grading by commit hash (consistency)#101
a6b8 merged 1 commit into
mainfrom
memo-110-cli-pin-hash

Conversation

@a6b8

@a6b8 a6b8 commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Closes #100. Follow-up to #99.

Switches the flowmcp-grading pin from the #v2.4.0 tag to the commit hash it resolves to (f8bededa2328e09198930367046ca9e4885f4744), matching the hash-pinned sibling deps (flowmcp-core, geo-*-toolkit) and removing tag-mutability risk.

  • No code/behaviour change — identical commit, grading stays 2.4.0.
  • package-lock.json resolved SHA was already f8beded; this only aligns the package.json spec + the lock's spec mirror so npm ci stays in sync.
  • Verified locally: npm ci clean, grading suites green.

🤖 Generated with Claude Code

Switch the grading pin from the v2.4.0 tag to the commit hash it points
at (f8beded), matching the hash-pinned sibling deps and removing the
tag-mutability risk. Same commit -> no behaviour change. Lockfile resolved
SHA was already f8beded; this only aligns the package.json spec + lock mirror.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@a6b8
a6b8 merged commit 58eef41 into main Jun 5, 2026
1 check passed
@a6b8
a6b8 deleted the memo-110-cli-pin-hash branch June 5, 2026 16:57
@codecov

codecov Bot commented Jun 5, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pin flowmcp-grading by commit hash (consistency)

1 participant